Housekeeping Longtime Archive

To not flood / overcrowd the Orchestra runtime database runtime data will be deleted or archived to an special archive database after a certain period of time. This is adjustable in Orchestra configuration files. This means that the information for past interface processes are not infinitely available in the monitor. Therefore, it is recommend to introduce additional runtime logs containing the important information’s of the interface and store them in individual files or database tables resp. a archive database.

The following elements are automatically cleaned:

• Messages

• Process-information

• System events

The periods how often and how long the information is kept in the runtime database can be configured in the environment settings of the server. Please refer to this chapter for a detailed description of the parameters

Housekeeping and Longtime archive are tightly coupled. Depending if the longtime archiving option is active or not, the housekeeping deletes or moves the information. In the latter case, when longtime archiving is active, the process-information and messages are automatically moved to longtime database. This longtime database consists of a database for the meta data and a filesystem folder that is used to store the detail information. All files in the folder are automatically added to a zip file. This is necessary in order to reduce waste of disk space. Also the longtime archive is automatically cleaned. After a given period in time, the archive entries are deleted from the database. The folders are also cleared automatically.